feat: Add Support for Ocsf v1.5 in ParseToOCSF#36603
feat: Add Support for Ocsf v1.5 in ParseToOCSF#36603
Conversation
There was a problem hiding this comment.
The pull request linter fails with the following errors:
❌ Features must contain a change to a README file.
❌ Features must contain a change to an integration test file and the resulting snapshot.
❌ The first word of the pull request title should not be capitalized. If the title starts with a CDK construct, it should be in backticks "``".
If you believe this pull request should receive an exemption, please comment and provide a justification. A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed, add Clarification Request to a comment.
|
This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. Note that PRs with failing linting check or builds are not reviewed, please ensure your build is passing To prevent automatic closure:
This PR will automatically close in 14 days if no action is taken. |
|
This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error. |
|
Comments on closed issues and PRs are hard for our team to see. |
Issue # (if applicable)
N/A
Closes #.
N/A
Reason for this change
ParseToOCSF processor converts logs into OCSF format, and previously it supported OCSF version 1.1. This change adds support for a new version - OCSF version 1.5 to the existing OCSF feature. For the new version, We add a new value to the existing OCSF Version parameter, and have a new optional parameter called MappingVersion .
Description of changes
mappingVersion.Describe any new or updated permissions being added
N/A
Description of how you validated changes
Added tests
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license